home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Arsenal Files 1
/
The Arsenal Files (Arsenal Computer).ISO
/
bbs
/
tm0203.txt
< prev
next >
Wrap
Text File
|
1994-01-23
|
2KB
|
51 lines
SEA Technical Memorandum #0203, SEAdog 4.50; Event Scheduling
Last updated: December 8, 1988
Copyright 1988 by System Enhancement Associates, Inc.
SEAdog 4.50
Event Scheduling
SEAdog version 4.50 implements event scheduling in a slightly different way
than earlier versions. The difference is such that it is only significant
if overlapping events are defined.
In earlier versions the SEAdog mailer would not exit a mail event until
that event ended of its own accord. This is no longer true. The mailer
will now exit a mail event in order to execute another event that was
defined earlier in the configuration file. For example, consider the
following event definitions:
Event A all 04:00 05:00
Event B all 03:00 06:00
In the past, event A would never be executed, since event B totally
blanketed it. Now, however, the mailer will begin executing event B at
03:00, then exit event B and begin event A at 04:00, then exit event A and
begin event B again at 05:00, then exit event B again at 06:00.
This is especially useful for "triggered" external events, even more so as
the mailer now unpacks packets on the fly, as time permits.
In general terms, at any given time the mailer will execute the first
active event it sees (scanning down from the top of the configuration file)
where it is in the event window for that event. Thus, consider a counter-
example:
Event B all 03:00 06:00
Event A all 04:00 05:00
In this case (which is just the first example with the order changed),
event A will never be executed, since event B will now totally blanket it.
But if event B were made dynamic, like so:
Event B all 03:00 06:00 dynamic
Event A all 04:00 05:00
then event A will run whenever event B finishes with all dialing any time
before 05:00.